Enhance documentation on using Promises in Client Components with use
#8294
Conversation
This commit adds important guidelines regarding the caching and stability of Promises passed to the `use` API in Client Components. It includes examples demonstrating how to properly cache Promises to prevent components from re-suspending on every render, as well as addressing pitfalls related to using uncached and chained Promises.
|
Hi @MaxwellCohen! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
1 participant
This commit adds guidelines regarding the caching and stability of Promises passed to the
useAPI in Client Components. It includes examples that demonstrate how to cache Promises to prevent components from resuspending on every render, and how to avoid pitfalls when using uncached or chained Promises.If there are any changes wanted, I will gladly make them, or if this is not wanted, feel free to close this PR
AI transparancy notice: I leveraged Cursor auto AI to help write these changes
This is how I would resolve Issue #8290